home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The CICA Windows Explosion!
/
The CICA Windows Explosion! - Disc 2.iso
/
nt
/
ntkb.zip
/
NTKB.EXE
/
Q104
/
1
/
61.TXT
< prev
next >
Wrap
Text File
|
1993-11-16
|
4KB
|
106 lines
DOCUMENT:Q104161 04-NOV-1993 [W_NT]
TITLE :Users Moved to Another Group May Lose Persistent Connections
PRODUCT :Windows NT
PROD/VER:3.10
OPER/SYS:WINDOWS
KEYWORDS:buglist3.10
----------------------------------------------------------------------
The information in this article applies to:
- Microsoft Windows NT operating system version 3.1
- Microsoft Windows NT Advanced Server version 3.1
----------------------------------------------------------------------
SYMPTOMS
========
While you are using Microsoft Windows NT, if you move a User from one
User Group to another User Group, this may cause the User's previous
persistent connections to be lost. Once in the new User Group, any
network connection made may not be persistent.
For example: A user who starts out in the Administrators group and is
then moved to the Power Users group loses persistent connection
functionality. The connections while in the Power Users group will
never be persistent.
STATUS
======
Microsoft has confirmed this to be a problem in Windows NT version 3.1
and Windows NT Advanced Server version 3.1. We are researching this
problem and will post new information here in the Microsoft Knowledge
Base as it becomes available.
MORE INFORMATION
================
Steps to Reproduce Problem
--------------------------
1. Logon to a Windows NT computer as an Administrator.
2. In the User Manager, create a new user "Test" and add it to the
Administrators group. Set any desired password.
3. Log off and then log on as "Test."
4. In File Manager, verify that Reconnect At Logon is selected in
the Connect Network Drive dialog box.
5. From the Disk menu, choose Connect Network Drive to connect
drive X to \\SERVER1\SHARE (whatever server is available).
6. Log off and then log on again as "Test." Drive X will be
reconnected to \\SERVER1\SHARE.
7. Log off, then log on as an Administrator.
8. In the User Manager, remove the "Test" user from the
Administrators group and add "Test" to the Power Users group.
9. Log off and then log on as "Test." Drive X will not be reconnected
to \\SERVER1\SHARE.
10. In File Manager, verify that Reconnect At Logon is STILL selected,
and connect drive Y to \\SERVER2\SHARE.
11. Log off and then log on as "Test" again. Neither drive X nor drive
Y is reconnected even though in File Manager, Reconnect At Logon is
still selected.
In the Registry, HKEY_CURRENT_USER\Software\Microsoft\Windows
NT\CurrentVersion\Network\Persistent Connections lists both
\\SERVER1\SHARE and \\SERVER2\SHARE, and Save Connections=YES,
but HKEY_CURRENT_USER\Network\P and Q are unavailable.
12. Log off and then log on as an Administrator.
13. Move "Test" out of the Power Users group and back into the
Administrators group.
14. Log off and then log on as "Test". X: will be reconnected.
Subsequent network connections while "Test" is an Administrator
will be persistent if Connect At Logon is selected.
Additional reference words: 3.10
KBCategory:
KBSubcategory: netsrv
=============================================================================
THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS
PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS
ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO
EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR
ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL,
CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF
MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION
OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES
SO THE FOREGOING LIMITATION MAY NOT APPLY.
Copyright Microsoft Corporation 1993.